• what are we doing here?

We are removing the support for labeled sources coupled with profile based sources

• What is the current way of doing things?

Currently, when we read some sources by labels, we would get their names. For example:

apiVersion: v1
kind: ConfigMap
metadata:
  labels:
    color: red
  name: paint

when we search by labels : color: red, we will find and read this configmap.

But, if includeProfileSpecificSources exists, we would read all other configmaps matching this profile. For example, if active profiles : [dev, k8s], then we would also try to read:

paint-dev
paint-k8s

• Why is this a problem and we have to drop such support?

This has been talked here

@ryanjbaxter this is ready also, and unlike the previous ones, is more substantial.